Preparing the Helix QAC Visual Studio Plug-in prior to Synchronization
The plug-in options are as follows:
-p, --vsproj <VSProjectFullName> [Required]
You can specify the full path to the Visual Studio project. A single Helix QAC project will be created that includes all the files from the Visual Studio projects specified with this option. A list of Visual Studio projects can be sent for synchronization, as follows:
-c, --cfg <ConfigurationName|PlatformName> [Optional]
You can specify the Visual Studio Configuration for which the Helix QAC project will be created, using the format <ConfigurationName|PlatformName>
- for example: "Debug|Win32", "Release|x86", "Debug|AnyCPU"
. If no Configuration name is given, then the active Configuration from the Solution will be used. This option should not be used if the -t
and -f
options are used.
Alternatively use the following 2 options to specify the Visual Studio configuration name and platform:
-t, --cfgType <ConfigurationName> [Optional]
where <ConfigurationName> is one of the Visual Studio project configuration names eg;_ Debug, Release-f, --cfgPlatform <PlatformName> [Optional]
where <PlatformName> is one of the Visual Studio platform names eg:- Win32, x86, x64 etc
-t
and -f
options together instead of the -c
option. Do not use singly.-s, --solutionDir
You can specify the solution directory, this may be required where a project uses common properties shared with other projects within the solution.
--solutionDir C:\Users\ccarr\AppData\Local\Perforce\Helix-QAC-2020.2\samples\sample_ VS19x86-2020.2\src\
Contents of Helix QAC project:
- All Definitions extracted from the VS project, including the predefined ones.
- All project and system Include Paths.
- Pre-compiled headers for C++ projects.
- All files with extensions supported by Helix QAC.
- All files included in the build for the specified configuration.